Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96d19ba7ea98b7e1dc6c3423561331ccf8a6f0346a2c4ade918a230a9a836acb

Tx prefix hash: f55a9cd5504e95f1749ee7ef1a36835b0e884705ee0bc607f47e08e59546e6db
Tx public key: dce1296f519b8302c432c79d8754a1a25f30df78327898637abd2b90d285041f
Timestamp: 1712580097 Timestamp [UCT]: 2024-04-08 12:41:37 Age [y:d:h:m:s]: 01:037:18:30:24
Block: 996011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288000 RingCT/type: yes/0
Extra: 01dce1296f519b8302c432c79d8754a1a25f30df78327898637abd2b90d285041f02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c235720b6fb6b6b72bc5239c18b90ff654543b4f9cfc42a8d7bfa024846c795 0.600000000000 1456427 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": 996021, "vin": [ { "gen": { "height": 996011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c235720b6fb6b6b72bc5239c18b90ff654543b4f9cfc42a8d7bfa024846c795" } } ], "extra": [ 1, 220, 225, 41, 111, 81, 155, 131, 2, 196, 50, 199, 157, 135, 84, 161, 162, 95, 48, 223, 120, 50, 120, 152, 99, 122, 189, 43, 144, 210, 133, 4, 31, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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