Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 469ce900d177ed3fadbec57940fb41dcb90fe8af40521ffdd2b01a3f856d2110

Tx prefix hash: d80549dec79be1c5d5d772c2eb1f6fcde6f08a738bbdfea1c605663007c5730c
Tx public key: b2885395c1c4ad8f0eccb78da5c387b120b911b7655e04663c1a33ba7444f88f
Timestamp: 1717039415 Timestamp [UCT]: 2024-05-30 03:23:35 Age [y:d:h:m:s]: 00:154:21:15:02
Block: 1033010 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110871 RingCT/type: yes/0
Extra: 01b2885395c1c4ad8f0eccb78da5c387b120b911b7655e04663c1a33ba7444f88f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d803ef1cd0d5b1c19a5e745a7846789cb9a761a0046e17d3d13f2257210588ba 0.600000000000 1501467 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": 1033020, "vin": [ { "gen": { "height": 1033010 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d803ef1cd0d5b1c19a5e745a7846789cb9a761a0046e17d3d13f2257210588ba" } } ], "extra": [ 1, 178, 136, 83, 149, 193, 196, 173, 143, 14, 204, 183, 141, 165, 195, 135, 177, 32, 185, 17, 183, 101, 94, 4, 102, 60, 26, 51, 186, 116, 68, 248, 143, 2, 17, 0, 0, 0, 1, 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