Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fbfbd51974cc23a552979636d103fa6fca11d8a3928008f94fa99b73a4da1da

Tx prefix hash: 562dbad6add2b7c2357c3871ef154fa11018ee8f9c31593a395f33447b61a100
Tx public key: 026f3441470126ad209f5bdbd5e0ef28d7e9c6d54fc8d7b1f42706d7c237eb4f
Timestamp: 1722882020 Timestamp [UCT]: 2024-08-05 18:20:20 Age [y:d:h:m:s]: 00:223:08:38:41
Block: 1081450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159525 RingCT/type: yes/0
Extra: 01026f3441470126ad209f5bdbd5e0ef28d7e9c6d54fc8d7b1f42706d7c237eb4f02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fb6a17c0b0cb8640190ce1a74177033522ec0d011cb7e78539e6e8aa04de2812 0.600000000000 1555197 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": 1081460, "vin": [ { "gen": { "height": 1081450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fb6a17c0b0cb8640190ce1a74177033522ec0d011cb7e78539e6e8aa04de2812" } } ], "extra": [ 1, 2, 111, 52, 65, 71, 1, 38, 173, 32, 159, 91, 219, 213, 224, 239, 40, 215, 233, 198, 213, 79, 200, 215, 177, 244, 39, 6, 215, 194, 55, 235, 79, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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