Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70dbc9819087390877a854273618b8b13176b19e20e0263ef104bce0bffa994d

Tx prefix hash: a76c4cde63a1f5a2669224a3766d7f968e6fb265464df0d0000ced34e9a592df
Tx public key: 036d4d56ee04ea7d6bc4675690a9b6aebc756938ec3301a6775b68d627cab74e
Timestamp: 1733836086 Timestamp [UCT]: 2024-12-10 13:08:06 Age [y:d:h:m:s]: 00:114:12:49:37
Block: 1172168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81632 RingCT/type: yes/0
Extra: 01036d4d56ee04ea7d6bc4675690a9b6aebc756938ec3301a6775b68d627cab74e0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eda75a4a805670582a944811d0c4dcfe1d02ed8ba0e433c411a5956e987ab3e2 0.600000000000 1658025 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": 1172178, "vin": [ { "gen": { "height": 1172168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eda75a4a805670582a944811d0c4dcfe1d02ed8ba0e433c411a5956e987ab3e2" } } ], "extra": [ 1, 3, 109, 77, 86, 238, 4, 234, 125, 107, 196, 103, 86, 144, 169, 182, 174, 188, 117, 105, 56, 236, 51, 1, 166, 119, 91, 104, 214, 39, 202, 183, 78, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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