Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 963917dcd328d399f8c1cca2f395950235cd1a05a1f0843cbd9fdce39b793dcc

Tx prefix hash: cbb3184263cb1ebaa69323d31475353306416d67d02bb1ccd6bfef0c9c94f9f7
Tx public key: 053cc651872edfd2c9952b22c0dfc69ac6d2a9ed2907fff7a9ec4a34928a7dcc
Timestamp: 1729514954 Timestamp [UCT]: 2024-10-21 12:49:14 Age [y:d:h:m:s]: 01:042:16:41:38
Block: 1136403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288936 RingCT/type: yes/0
Extra: 01053cc651872edfd2c9952b22c0dfc69ac6d2a9ed2907fff7a9ec4a34928a7dcc0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f2517b8751ded2c360879ff676841a5e538af88f3be8e760eb675ab3164bcfc 0.600000000000 1619748 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": 1136413, "vin": [ { "gen": { "height": 1136403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f2517b8751ded2c360879ff676841a5e538af88f3be8e760eb675ab3164bcfc" } } ], "extra": [ 1, 5, 60, 198, 81, 135, 46, 223, 210, 201, 149, 43, 34, 192, 223, 198, 154, 198, 210, 169, 237, 41, 7, 255, 247, 169, 236, 74, 52, 146, 138, 125, 204, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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