Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 353e24df7c81d7c542d3700123d0bd8cb68810eff33c33b2b0d936bdeb08f22e

Tx prefix hash: 7a63517430557fc2f244fde4395a96545537218b4e8bf4ab4609a909d81bf73b
Tx public key: a73150f8464eaa8997e8a9f1e9d0aa4259fe04321bb6ca3fd3a125f4ae0c34e3
Timestamp: 1669077610 Timestamp [UCT]: 2022-11-22 00:40:10 Age [y:d:h:m:s]: 01:364:12:33:53
Block: 636282 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521555 RingCT/type: yes/0
Extra: 01a73150f8464eaa8997e8a9f1e9d0aa4259fe04321bb6ca3fd3a125f4ae0c34e302110000000374b6d784000000000000000000

1 output(s) for total of 4.783365947000 dcy

stealth address amount amount idx
00: 3d4a8ba0918fd5ae1d44d9ae9b5f11dbb1c8d40bad1ce1d1666d36ca3ba33550 4.783365947000 1075698 of 0

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": 636292, "vin": [ { "gen": { "height": 636282 } } ], "vout": [ { "amount": 4783365947, "target": { "key": "3d4a8ba0918fd5ae1d44d9ae9b5f11dbb1c8d40bad1ce1d1666d36ca3ba33550" } } ], "extra": [ 1, 167, 49, 80, 248, 70, 78, 170, 137, 151, 232, 169, 241, 233, 208, 170, 66, 89, 254, 4, 50, 27, 182, 202, 63, 211, 161, 37, 244, 174, 12, 52, 227, 2, 17, 0, 0, 0, 3, 116, 182, 215, 132, 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