Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 878f9abd9617199cf436f542b45d78165a8dae80141ab7e21efa43548ab1aea5

Tx prefix hash: 26c0b949afc6e911bdab9591c82e0b59b9ebc967979f7494eb512cf36eb9df6a
Tx public key: 7a027ebb211edec148975f9d1bb97f1d6c43f1534a8d74bda9f1c7c5c6ba3719
Timestamp: 1720032615 Timestamp [UCT]: 2024-07-03 18:50:15 Age [y:d:h:m:s]: 00:279:21:36:03
Block: 1057820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199990 RingCT/type: yes/0
Extra: 017a027ebb211edec148975f9d1bb97f1d6c43f1534a8d74bda9f1c7c5c6ba37190211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42ce1be9a0e381ef4e61a04c3240911f55907bfc2111470365db21f1ddc27096 0.600000000000 1528261 of 15

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": 1057830, "vin": [ { "gen": { "height": 1057820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42ce1be9a0e381ef4e61a04c3240911f55907bfc2111470365db21f1ddc27096" } } ], "extra": [ 1, 122, 2, 126, 187, 33, 30, 222, 193, 72, 151, 95, 157, 27, 185, 127, 29, 108, 67, 241, 83, 74, 141, 116, 189, 169, 241, 199, 197, 198, 186, 55, 25, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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