Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9eb4d4ad2493331b94635a729e53cc52509180449b9aea882392f130b10aa106

Tx prefix hash: b59353cb5584c7911d6df9035fdd831d2ee29386f5d8e707f5fb0279466e49f2
Tx public key: 32f4f291e75db7443024a54b8a3b151045383b91baf0a3f157176c5e8e60ff52
Timestamp: 1705329688 Timestamp [UCT]: 2024-01-15 14:41:28 Age [y:d:h:m:s]: 01:078:01:06:35
Block: 935916 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316879 RingCT/type: yes/0
Extra: 0132f4f291e75db7443024a54b8a3b151045383b91baf0a3f157176c5e8e60ff520211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e35c24cad83395bead7508053b4778695a699d1d1eb9d40f5c3f6b4400f28d39 0.600000000000 1393934 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": 935926, "vin": [ { "gen": { "height": 935916 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e35c24cad83395bead7508053b4778695a699d1d1eb9d40f5c3f6b4400f28d39" } } ], "extra": [ 1, 50, 244, 242, 145, 231, 93, 183, 68, 48, 36, 165, 75, 138, 59, 21, 16, 69, 56, 59, 145, 186, 240, 163, 241, 87, 23, 108, 94, 142, 96, 255, 82, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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