Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c3985a24af264d237bcd3ee22b0084983c219151e460e1928d7afd3dd2bff46

Tx prefix hash: b6fd044febea0e9a75b0adb8117a6a5739ea5c82421b373554c6ff288d1c568c
Tx public key: 8db40f5d1d9b89c3f80dab88e93d59b234369aef3de4bb6f52dc440139398158
Timestamp: 1718522046 Timestamp [UCT]: 2024-06-16 07:14:06 Age [y:d:h:m:s]: 00:281:09:28:05
Block: 1045318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201054 RingCT/type: yes/0
Extra: 018db40f5d1d9b89c3f80dab88e93d59b234369aef3de4bb6f52dc44013939815802110000000136ea7c8b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1212e6a354c54e657dde4e9f6fa316570211ade021ef7ba26e0897d37ad193f 0.600000000000 1514855 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": 1045328, "vin": [ { "gen": { "height": 1045318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1212e6a354c54e657dde4e9f6fa316570211ade021ef7ba26e0897d37ad193f" } } ], "extra": [ 1, 141, 180, 15, 93, 29, 155, 137, 195, 248, 13, 171, 136, 233, 61, 89, 178, 52, 54, 154, 239, 61, 228, 187, 111, 82, 220, 68, 1, 57, 57, 129, 88, 2, 17, 0, 0, 0, 1, 54, 234, 124, 139, 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