Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 996e4871a20abdba4814ecf1081929ed0d8e28748d84ba4d09018d4f0258b27b

Tx prefix hash: 0500d2fff34ebdafa727d0fabc94308a7b5f715fadeee661067815e52f226ebd
Tx public key: 802df02fd3a3ed017be5464ada2489a04e37e24c55fe432c92f735119457f16d
Timestamp: 1718062105 Timestamp [UCT]: 2024-06-10 23:28:25 Age [y:d:h:m:s]: 00:257:15:12:46
Block: 1041502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184056 RingCT/type: yes/0
Extra: 01802df02fd3a3ed017be5464ada2489a04e37e24c55fe432c92f735119457f16d021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b9ce3c8d8adc3d124c44b5c1df4824ed1b65a90ed9316d40be0fcaeeb7b9abc 0.600000000000 1510193 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": 1041512, "vin": [ { "gen": { "height": 1041502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b9ce3c8d8adc3d124c44b5c1df4824ed1b65a90ed9316d40be0fcaeeb7b9abc" } } ], "extra": [ 1, 128, 45, 240, 47, 211, 163, 237, 1, 123, 229, 70, 74, 218, 36, 137, 160, 78, 55, 226, 76, 85, 254, 67, 44, 146, 247, 53, 17, 148, 87, 241, 109, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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