Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbec072215d284d88c96eeaff1431e924099c29d7456b5e1c5d290f9a9a0ac9d

Tx prefix hash: 262da0cd35007cf9bc763a193a2a2cd8e99ac53686d248895e597cffef735bcf
Tx public key: 647cf6590d17dbe2fea9a6bde951dd6d8a58ce9052fd47c080b6cf32f276329f
Timestamp: 1732749488 Timestamp [UCT]: 2024-11-27 23:18:08 Age [y:d:h:m:s]: 00:132:23:53:00
Block: 1163158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94857 RingCT/type: yes/0
Extra: 01647cf6590d17dbe2fea9a6bde951dd6d8a58ce9052fd47c080b6cf32f276329f0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 006b692e3421ecf43bb08ea19a763473e1cd0833c44b9b267befbf18ed58621f 0.600000000000 1648825 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": 1163168, "vin": [ { "gen": { "height": 1163158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "006b692e3421ecf43bb08ea19a763473e1cd0833c44b9b267befbf18ed58621f" } } ], "extra": [ 1, 100, 124, 246, 89, 13, 23, 219, 226, 254, 169, 166, 189, 233, 81, 221, 109, 138, 88, 206, 144, 82, 253, 71, 192, 128, 182, 207, 50, 242, 118, 50, 159, 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