Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61c79d0596cd6c620ca6f4c35dd777fc61739694236c14a250d28392f56248b9

Tx prefix hash: 23181183825d3f841ab1cf75e259a8e31bec8bf40dca2d48f1947db4b3983f1e
Tx public key: 1e7c241ca3d0e8f0fd8d83d8ffff8d6d3e4f51b1e51bfcc36796a427f144cf1e
Timestamp: 1580017335 Timestamp [UCT]: 2020-01-26 05:42:15 Age [y:d:h:m:s]: 04:256:06:49:08
Block: 53264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1073143 RingCT/type: yes/0
Extra: 011e7c241ca3d0e8f0fd8d83d8ffff8d6d3e4f51b1e51bfcc36796a427f144cf1e021100000001dcee4b4d000000000000000000

1 output(s) for total of 408.819981710000 dcy

stealth address amount amount idx
00: 4b4c7d933cd108e579394423dccbaee16a6b8aa63af7d5b7196312326e943842 408.819981710000 98690 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": 53274, "vin": [ { "gen": { "height": 53264 } } ], "vout": [ { "amount": 408819981710, "target": { "key": "4b4c7d933cd108e579394423dccbaee16a6b8aa63af7d5b7196312326e943842" } } ], "extra": [ 1, 30, 124, 36, 28, 163, 208, 232, 240, 253, 141, 131, 216, 255, 255, 141, 109, 62, 79, 81, 177, 229, 27, 252, 195, 103, 150, 164, 39, 241, 68, 207, 30, 2, 17, 0, 0, 0, 1, 220, 238, 75, 77, 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