Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6962c748930e3b967994bf7c6943be9ca304196dd07f758d85473e1e27d254b

Tx prefix hash: 7c283a47ae4064540bbee301607dae27deb0195db9ac3b7eb6c9cda145ef1115
Tx public key: 8646c948cfb5c963b7a1cb0b9d0ed629dacf3633c2edadde2291a9d9601edba0
Timestamp: 1702327647 Timestamp [UCT]: 2023-12-11 20:47:27 Age [y:d:h:m:s]: 01:188:23:26:47
Block: 911051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396127 RingCT/type: yes/0
Extra: 018646c948cfb5c963b7a1cb0b9d0ed629dacf3633c2edadde2291a9d9601edba002110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8591d22660e3488c84d0717e20f72d87597ba2b822c6cdac501f3b929cf4c5db 0.600000000000 1368226 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": 911061, "vin": [ { "gen": { "height": 911051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8591d22660e3488c84d0717e20f72d87597ba2b822c6cdac501f3b929cf4c5db" } } ], "extra": [ 1, 134, 70, 201, 72, 207, 181, 201, 99, 183, 161, 203, 11, 157, 14, 214, 41, 218, 207, 54, 51, 194, 237, 173, 222, 34, 145, 169, 217, 96, 30, 219, 160, 2, 17, 0, 0, 0, 2, 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