Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 282abb221386d58a86b637227fdd0b2cb9a625c4ea7e6212a2f3806ab90c8d1f

Tx prefix hash: c73ddc9a3c8589b40100ce1bd8a924c57cead50ff8644ed2acab1800871fdb15
Tx public key: 001c3f0d2f7b880af8da45074613f631406c83af77575add51e1cf9d2c772a0d
Timestamp: 1704467159 Timestamp [UCT]: 2024-01-05 15:05:59 Age [y:d:h:m:s]: 01:124:03:05:07
Block: 928764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349835 RingCT/type: yes/0
Extra: 01001c3f0d2f7b880af8da45074613f631406c83af77575add51e1cf9d2c772a0d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed07859c7637c157c9651d24b871e8c4a85bbe79e33c5b1733bba91613e92fca 0.600000000000 1386626 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": 928774, "vin": [ { "gen": { "height": 928764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed07859c7637c157c9651d24b871e8c4a85bbe79e33c5b1733bba91613e92fca" } } ], "extra": [ 1, 0, 28, 63, 13, 47, 123, 136, 10, 248, 218, 69, 7, 70, 19, 246, 49, 64, 108, 131, 175, 119, 87, 90, 221, 81, 225, 207, 157, 44, 119, 42, 13, 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