Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f6920a41d4f62bef9de8d2332143d2d326cf0dda410661c7234ba2388af7f8b

Tx prefix hash: 6c773524624cd2fabaedc6db07484cc29ea19710b540df04ff72d006bf9f5c1c
Tx public key: af0832419267e9c860c498ba32eea9fc44fc2145b29f8432a06276fd69ca1aa8
Timestamp: 1715541108 Timestamp [UCT]: 2024-05-12 19:11:48 Age [y:d:h:m:s]: 00:325:02:56:31
Block: 1020614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232357 RingCT/type: yes/0
Extra: 01af0832419267e9c860c498ba32eea9fc44fc2145b29f8432a06276fd69ca1aa8021100000003c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae8651d4ed8571d77375c6d92bd22a60f3cd7e22ae794c6e25e3a2ed8ff61042 0.600000000000 1484695 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": 1020624, "vin": [ { "gen": { "height": 1020614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae8651d4ed8571d77375c6d92bd22a60f3cd7e22ae794c6e25e3a2ed8ff61042" } } ], "extra": [ 1, 175, 8, 50, 65, 146, 103, 233, 200, 96, 196, 152, 186, 50, 238, 169, 252, 68, 252, 33, 69, 178, 159, 132, 50, 160, 98, 118, 253, 105, 202, 26, 168, 2, 17, 0, 0, 0, 3, 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