Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e45f90e5a939e35a97f9d7898d95caef6322d989d9196242fd61b0e50c17cbe9

Tx prefix hash: 90d87927b69a3b0bf88321d5034160be6e4b1cbdf509e57dccbd097ab1d873c2
Tx public key: 80bf9c661977577b18e7d64c13fd121a9d9fcae2d107aece5caece41c81e458a
Timestamp: 1736670368 Timestamp [UCT]: 2025-01-12 08:26:08 Age [y:d:h:m:s]: 00:064:02:50:51
Block: 1195620 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45619 RingCT/type: yes/0
Extra: 0180bf9c661977577b18e7d64c13fd121a9d9fcae2d107aece5caece41c81e458a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c3e64df448fc177240fcf01d6e3d89948ccedc07674ce3c984f1ba8592caa82b 0.600000000000 1682211 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": 1195630, "vin": [ { "gen": { "height": 1195620 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c3e64df448fc177240fcf01d6e3d89948ccedc07674ce3c984f1ba8592caa82b" } } ], "extra": [ 1, 128, 191, 156, 102, 25, 119, 87, 123, 24, 231, 214, 76, 19, 253, 18, 26, 157, 159, 202, 226, 209, 7, 174, 206, 92, 174, 206, 65, 200, 30, 69, 138, 2, 17, 0, 0, 0, 2, 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