Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 242833c1ca8f770218b039ebf0f34c5489a49dba87edde3d6796e4989e8f1f51

Tx prefix hash: 787ca41252656e737acb30057ba0164fdda6702010f22c367a2889c6b07f1aeb
Tx public key: 3624038aa5f770a2fd21b976c2c410a7de508f7c945fb1f7a68fde1e006a938c
Timestamp: 1696221457 Timestamp [UCT]: 2023-10-02 04:37:37 Age [y:d:h:m:s]: 01:190:11:27:54
Block: 860627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397175 RingCT/type: yes/0
Extra: 013624038aa5f770a2fd21b976c2c410a7de508f7c945fb1f7a68fde1e006a938c02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.863744961000 dcy

stealth address amount amount idx
00: 33f8a41aa4f8cbc416e53238c2a65a4ddb28d74f72215c7022cf930f0ae3b280 0.863744961000 1314917 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": 860637, "vin": [ { "gen": { "height": 860627 } } ], "vout": [ { "amount": 863744961, "target": { "key": "33f8a41aa4f8cbc416e53238c2a65a4ddb28d74f72215c7022cf930f0ae3b280" } } ], "extra": [ 1, 54, 36, 3, 138, 165, 247, 112, 162, 253, 33, 185, 118, 194, 196, 16, 167, 222, 80, 143, 124, 148, 95, 177, 247, 166, 143, 222, 30, 0, 106, 147, 140, 2, 17, 0, 0, 0, 1, 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