Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f853ca827fe394f726b34b008e582ce6267bb548eed0062f72de1abc259d0912

Tx prefix hash: 5779d3b3d893c3597d3ad2c7fcbb41de72a535433ee92856eb5d06be67f1def8
Tx public key: 0b0e7d993a921efc750322c1545e16b52b0ac3127db2b801bccf538a14f2bbef
Timestamp: 1748356701 Timestamp [UCT]: 2025-05-27 14:38:21 Age [y:d:h:m:s]: 00:177:18:33:39
Block: 1292108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124734 RingCT/type: yes/0
Extra: 010b0e7d993a921efc750322c1545e16b52b0ac3127db2b801bccf538a14f2bbef02110000000586ae2f0d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2aaa8b2c892637c80a946cf7b6675e483f363b2102fcae31a87ced7e4de959ae 0.600000000000 1779579 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": 1292118, "vin": [ { "gen": { "height": 1292108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2aaa8b2c892637c80a946cf7b6675e483f363b2102fcae31a87ced7e4de959ae" } } ], "extra": [ 1, 11, 14, 125, 153, 58, 146, 30, 252, 117, 3, 34, 193, 84, 94, 22, 181, 43, 10, 195, 18, 125, 178, 184, 1, 188, 207, 83, 138, 20, 242, 187, 239, 2, 17, 0, 0, 0, 5, 134, 174, 47, 13, 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