Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e24bc891ce1638fc945d409ede30b8a399d6d4c5a0625b642ae3889d7ee5297f

Tx prefix hash: 022d32f13c9786ad7fd65260d2986a3bba7dfea4b6dfda4953c1c22f93819a0e
Tx public key: 1115ad39f1a44dcd0a39f1962d1c98e6d42403f6228d7a89d517d77d25dd700a
Timestamp: 1698516524 Timestamp [UCT]: 2023-10-28 18:08:44 Age [y:d:h:m:s]: 02:011:15:26:04
Block: 879662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 527898 RingCT/type: yes/0
Extra: 011115ad39f1a44dcd0a39f1962d1c98e6d42403f6228d7a89d517d77d25dd700a021100000004faf35c9c000000000000000000

1 output(s) for total of 0.746989749000 dcy

stealth address amount amount idx
00: 61fa307aa84097434b1f96b20f47fb8d2e8731c19c90ed435f5da056eccaf3ea 0.746989749000 1335196 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": 879672, "vin": [ { "gen": { "height": 879662 } } ], "vout": [ { "amount": 746989749, "target": { "key": "61fa307aa84097434b1f96b20f47fb8d2e8731c19c90ed435f5da056eccaf3ea" } } ], "extra": [ 1, 17, 21, 173, 57, 241, 164, 77, 205, 10, 57, 241, 150, 45, 28, 152, 230, 212, 36, 3, 246, 34, 141, 122, 137, 213, 23, 215, 125, 37, 221, 112, 10, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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