Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1313400072cca8b447156098657d112c6daf3f6c9a7e10dfe2d32888e19480a5

Tx prefix hash: 4b684a5a3c4768adde14d3b01cf2f13e173fad3616eb7781aa2329b1c7702fc4
Tx public key: a62f09fc329b0a264c46e1e396ddae1f29d6a6f56ab327acd57e94bc81fde470
Timestamp: 1706655745 Timestamp [UCT]: 2024-01-30 23:02:25 Age [y:d:h:m:s]: 01:120:08:11:37
Block: 946903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347133 RingCT/type: yes/0
Extra: 01a62f09fc329b0a264c46e1e396ddae1f29d6a6f56ab327acd57e94bc81fde47002110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0d0cad06878df8c0c75ae45199556ad0a85c5952db4c3c61190b93af1096650 0.600000000000 1405247 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": 946913, "vin": [ { "gen": { "height": 946903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0d0cad06878df8c0c75ae45199556ad0a85c5952db4c3c61190b93af1096650" } } ], "extra": [ 1, 166, 47, 9, 252, 50, 155, 10, 38, 76, 70, 225, 227, 150, 221, 174, 31, 41, 214, 166, 245, 106, 179, 39, 172, 213, 126, 148, 188, 129, 253, 228, 112, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 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