Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fec7b76a61dab0230735713f76c41d7267a3880364a9594c3095e41b46e75c3d

Tx prefix hash: bae552ea5bab91563d2033ace11e51145363df273ead72ad53b0ec9b0df07bd7
Tx public key: 04013f18e5c7cedd306fbb5b06b6b6c7029bbf8d98790e4d5f831dcc0b9dbd46
Timestamp: 1719920571 Timestamp [UCT]: 2024-07-02 11:42:51 Age [y:d:h:m:s]: 01:099:02:28:46
Block: 1056899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 329314 RingCT/type: yes/0
Extra: 0104013f18e5c7cedd306fbb5b06b6b6c7029bbf8d98790e4d5f831dcc0b9dbd460211000000028fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e616a5f7678730a085a96212cc059811c0a43034d2d092c6cb851182cd5ffa3f 0.600000000000 1527328 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": 1056909, "vin": [ { "gen": { "height": 1056899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e616a5f7678730a085a96212cc059811c0a43034d2d092c6cb851182cd5ffa3f" } } ], "extra": [ 1, 4, 1, 63, 24, 229, 199, 206, 221, 48, 111, 187, 91, 6, 182, 182, 199, 2, 155, 191, 141, 152, 121, 14, 77, 95, 131, 29, 204, 11, 157, 189, 70, 2, 17, 0, 0, 0, 2, 143, 218, 155, 45, 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