Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ece5023b1f4a19ac776208e8ed4ed79090ea05c6592b4f100e2153982c760bf

Tx prefix hash: 09925dfe46b2c0cc878e24d03480fad06a36e0f397492c5b80cd76cbe256e5a7
Tx public key: c5f1393044882dbf4c090368b56d1edf5fd29b81e30ac3d4d0d91a5a5b8cdab1
Timestamp: 1700394142 Timestamp [UCT]: 2023-11-19 11:42:22 Age [y:d:h:m:s]: 01:134:15:27:45
Block: 895012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 357394 RingCT/type: yes/0
Extra: 01c5f1393044882dbf4c090368b56d1edf5fd29b81e30ac3d4d0d91a5a5b8cdab10211000000024b8f5122000000000000000000

1 output(s) for total of 0.664436830000 dcy

stealth address amount amount idx
00: 766fa54dfc55f1efcf49fefbd96e1b20df23b4798c26ee60153652454dc84066 0.664436830000 1351233 of 0

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": 895022, "vin": [ { "gen": { "height": 895012 } } ], "vout": [ { "amount": 664436830, "target": { "key": "766fa54dfc55f1efcf49fefbd96e1b20df23b4798c26ee60153652454dc84066" } } ], "extra": [ 1, 197, 241, 57, 48, 68, 136, 45, 191, 76, 9, 3, 104, 181, 109, 30, 223, 95, 210, 155, 129, 227, 10, 195, 212, 208, 217, 26, 90, 91, 140, 218, 177, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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