Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6762d1a1e372295e5b20387919ced452f914cdc22e3ae42276ebef9309d55e24

Tx prefix hash: 4b3034ce7f9cd42fde56a97123065b19f7336dabb8a8b6b690fad790425786d7
Tx public key: adf2c48147628e5eca87616dc55a83bc9d8c52411eceb48d6db7c981e0a22694
Timestamp: 1730652945 Timestamp [UCT]: 2024-11-03 16:55:45 Age [y:d:h:m:s]: 00:082:06:13:58
Block: 1145791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58804 RingCT/type: yes/0
Extra: 01adf2c48147628e5eca87616dc55a83bc9d8c52411eceb48d6db7c981e0a22694021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8b6bc90904651d69433d52d51c43a4f15a12f42ec172f356f5efdbd8b61ffda 0.600000000000 1630300 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": 1145801, "vin": [ { "gen": { "height": 1145791 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8b6bc90904651d69433d52d51c43a4f15a12f42ec172f356f5efdbd8b61ffda" } } ], "extra": [ 1, 173, 242, 196, 129, 71, 98, 142, 94, 202, 135, 97, 109, 197, 90, 131, 188, 157, 140, 82, 65, 30, 206, 180, 141, 109, 183, 201, 129, 224, 162, 38, 148, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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