Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 688952a54a84084bf2dcb1baf077711620fc01b4e8c10f0822fc235ebf8814fc

Tx prefix hash: 8e22e81c4df46b53c47a1d7e57fb41a7c1e7893f8dc5875fac297f04c18e5359
Tx public key: c883520e2f398c8960005993b1e3f35d1a7aecdc4a3b0d4009e2e8d7120a95c2
Timestamp: 1630604879 Timestamp [UCT]: 2021-09-02 17:47:59 Age [y:d:h:m:s]: 03:219:13:30:38
Block: 326072 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 931477 RingCT/type: yes/0
Extra: 01c883520e2f398c8960005993b1e3f35d1a7aecdc4a3b0d4009e2e8d7120a95c202110000007ecd14b6bf000000000000000000

1 output(s) for total of 51.002158592000 dcy

stealth address amount amount idx
00: 78905700076343e1cc3de8de76cfccc5f1cd79ce9e47c94aabff0d2adaaee0bd 51.002158592000 675695 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 326082, "vin": [ { "gen": { "height": 326072 } } ], "vout": [ { "amount": 51002158592, "target": { "key": "78905700076343e1cc3de8de76cfccc5f1cd79ce9e47c94aabff0d2adaaee0bd" } } ], "extra": [ 1, 200, 131, 82, 14, 47, 57, 140, 137, 96, 0, 89, 147, 177, 227, 243, 93, 26, 122, 236, 220, 74, 59, 13, 64, 9, 226, 232, 215, 18, 10, 149, 194, 2, 17, 0, 0, 0, 126, 205, 20, 182, 191, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8