Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74ebf7bc90801c9277b968927fa6d2fdf093f2cfb398bbc269da8d2a28987217

Tx prefix hash: 76a77ed5f08ffe7bda9da2031d737917510722d35cc9fd5dcd00ec5e2362b8ed
Tx public key: d252c8fc28fff0c2c3c9b181f8f25c60d31d6167985260c3a568a23a1e21a890
Timestamp: 1685353371 Timestamp [UCT]: 2023-05-29 09:42:51 Age [y:d:h:m:s]: 02:021:02:52:46
Block: 770569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 537088 RingCT/type: yes/0
Extra: 01d252c8fc28fff0c2c3c9b181f8f25c60d31d6167985260c3a568a23a1e21a89002110000000575e3f0e9000000000000000000

1 output(s) for total of 1.717058918000 dcy

stealth address amount amount idx
00: e2a892f215db383fc9ff3dd5ce6c8f0c74e07f31ef8cf616b04ab88f6be02d42 1.717058918000 1219890 of 0

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": 770579, "vin": [ { "gen": { "height": 770569 } } ], "vout": [ { "amount": 1717058918, "target": { "key": "e2a892f215db383fc9ff3dd5ce6c8f0c74e07f31ef8cf616b04ab88f6be02d42" } } ], "extra": [ 1, 210, 82, 200, 252, 40, 255, 240, 194, 195, 201, 177, 129, 248, 242, 92, 96, 211, 29, 97, 103, 152, 82, 96, 195, 165, 104, 162, 58, 30, 33, 168, 144, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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