Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5e0958d4e151fecd2c7daf0a44f4817cecf4b0b5a1b98ac2464c10d6dc6617e

Tx prefix hash: 4126f85697e626a26e43d168b7998646e9a29133878970c3ca79c5d2662675e5
Tx public key: 70c584b9121d2fee7028dc21a1233941516e701e11ea2d716e1b40a0a8b93af0
Timestamp: 1711545379 Timestamp [UCT]: 2024-03-27 13:16:19 Age [y:d:h:m:s]: 00:232:21:29:15
Block: 987484 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166712 RingCT/type: yes/0
Extra: 0170c584b9121d2fee7028dc21a1233941516e701e11ea2d716e1b40a0a8b93af00211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e00632f7387b28319542eaaf7a47377e600f0ca13fc5007501dc13f66c901445 0.600000000000 1447735 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": 987494, "vin": [ { "gen": { "height": 987484 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e00632f7387b28319542eaaf7a47377e600f0ca13fc5007501dc13f66c901445" } } ], "extra": [ 1, 112, 197, 132, 185, 18, 29, 47, 238, 112, 40, 220, 33, 161, 35, 57, 65, 81, 110, 112, 30, 17, 234, 45, 113, 110, 27, 64, 160, 168, 185, 58, 240, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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