Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fbe00d09336d026382aac2ae083d8992a98338e97d474a6728795491dd1ffa56

Tx prefix hash: 0b82704a7955d99c11f977b4f19b075e9e7ed985b0e1ace8cf3687421760b0e8
Tx public key: 7b91e9cf15480149167f88da7a5f07aa68d7eeb50e610dc41922667f2777e08d
Timestamp: 1715492970 Timestamp [UCT]: 2024-05-12 05:49:30 Age [y:d:h:m:s]: 00:320:21:41:29
Block: 1020219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229345 RingCT/type: yes/0
Extra: 017b91e9cf15480149167f88da7a5f07aa68d7eeb50e610dc41922667f2777e08d021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18a8d11c5e6d3c5a20884762f2645baf777dce5bb6aa40c133b60548ef058add 0.600000000000 1484280 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": 1020229, "vin": [ { "gen": { "height": 1020219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18a8d11c5e6d3c5a20884762f2645baf777dce5bb6aa40c133b60548ef058add" } } ], "extra": [ 1, 123, 145, 233, 207, 21, 72, 1, 73, 22, 127, 136, 218, 122, 95, 7, 170, 104, 215, 238, 181, 14, 97, 13, 196, 25, 34, 102, 127, 39, 119, 224, 141, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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