Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9237fe9980980035f456a7a3489f870d585f5682c7ecb44a2bfa3e9bad28a330

Tx prefix hash: 75c3f2a7bb78075ce463252dc91713b5f21be375df30ced2ce4de4e442386de5
Tx public key: 3fb9187bb3d619b2d8f42540852edd970beefd4aa41eeeed012047eeed43d2b6
Timestamp: 1695624391 Timestamp [UCT]: 2023-09-25 06:46:31 Age [y:d:h:m:s]: 01:221:20:06:28
Block: 855670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419625 RingCT/type: yes/0
Extra: 013fb9187bb3d619b2d8f42540852edd970beefd4aa41eeeed012047eeed43d2b602110000000775e3f0e9000000000000000000

1 output(s) for total of 0.897036538000 dcy

stealth address amount amount idx
00: 33d1fb42d2ec987c2c917d37fd8a72cb66e73838aad2a5e200d40038038816b1 0.897036538000 1309702 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": 855680, "vin": [ { "gen": { "height": 855670 } } ], "vout": [ { "amount": 897036538, "target": { "key": "33d1fb42d2ec987c2c917d37fd8a72cb66e73838aad2a5e200d40038038816b1" } } ], "extra": [ 1, 63, 185, 24, 123, 179, 214, 25, 178, 216, 244, 37, 64, 133, 46, 221, 151, 11, 238, 253, 74, 164, 30, 238, 237, 1, 32, 71, 238, 237, 67, 210, 182, 2, 17, 0, 0, 0, 7, 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