Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 377f9473f606d2f126ad033e35ef57080c52e710f3ae8a6cce7e3a2785b048d2

Tx prefix hash: acbd54952f192ab2f5b4981d00e80a0eb3915ae4d7f0b75caf20bd10a4c704e1
Tx public key: 62e32ccd14221f1053ebfbd30caa06b19230501d37d4d1f7141dd194b4dd514d
Timestamp: 1700795444 Timestamp [UCT]: 2023-11-24 03:10:44 Age [y:d:h:m:s]: 01:171:09:11:55
Block: 898334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383683 RingCT/type: yes/0
Extra: 0162e32ccd14221f1053ebfbd30caa06b19230501d37d4d1f7141dd194b4dd514d02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.647808329000 dcy

stealth address amount amount idx
00: 98d51eb2b847272e28a7e4c24fa1f5b5026def7149d35ab2789d9f36c9f7657f 0.647808329000 1354747 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": 898344, "vin": [ { "gen": { "height": 898334 } } ], "vout": [ { "amount": 647808329, "target": { "key": "98d51eb2b847272e28a7e4c24fa1f5b5026def7149d35ab2789d9f36c9f7657f" } } ], "extra": [ 1, 98, 227, 44, 205, 20, 34, 31, 16, 83, 235, 251, 211, 12, 170, 6, 177, 146, 48, 80, 29, 55, 212, 209, 247, 20, 29, 209, 148, 180, 221, 81, 77, 2, 17, 0, 0, 0, 6, 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