Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fc0da64f110085b35c5da9c6c8b7875b41ebe62254643c9f95548857214d4c3

Tx prefix hash: 1b275e40cb6e300126f5e304843e6bf05fcda2c81aa2141c42a7b2f0f6620561
Tx public key: 1e8f81f8a2ec50dd9d87dd7cf50ad7abbbb8336b4586a43d887a44ad8ed2e78f
Timestamp: 1702503046 Timestamp [UCT]: 2023-12-13 21:30:46 Age [y:d:h:m:s]: 01:037:19:23:26
Block: 912495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288344 RingCT/type: yes/0
Extra: 011e8f81f8a2ec50dd9d87dd7cf50ad7abbbb8336b4586a43d887a44ad8ed2e78f021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5726a5cf481366c3427c40d3d955bc83e45c51419a1e386a82b804b12164d35a 0.600000000000 1369723 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": 912505, "vin": [ { "gen": { "height": 912495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5726a5cf481366c3427c40d3d955bc83e45c51419a1e386a82b804b12164d35a" } } ], "extra": [ 1, 30, 143, 129, 248, 162, 236, 80, 221, 157, 135, 221, 124, 245, 10, 215, 171, 187, 184, 51, 107, 69, 134, 164, 61, 136, 122, 68, 173, 142, 210, 231, 143, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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