Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87a193ca56092934b3d0015969f9e4ba2590060362345fa7156b287dff2e487c

Tx prefix hash: d7f4c397b62cc62f01a4232c287b344ecbabb174882c77e6fe4d5c7132374507
Tx public key: b1ed3273fca2c1a96696b9df98d4313c05a2b7e8aff4f66046128e2ffbce0b36
Timestamp: 1725744316 Timestamp [UCT]: 2024-09-07 21:25:16 Age [y:d:h:m:s]: 00:077:10:50:23
Block: 1105177 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55382 RingCT/type: yes/0
Extra: 01b1ed3273fca2c1a96696b9df98d4313c05a2b7e8aff4f66046128e2ffbce0b3602110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ee18e2d1c38508b93fe9ca1a03cc9bbb7c3903e0119337791e8685d31b2cede9 0.600000000000 1582516 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": 1105187, "vin": [ { "gen": { "height": 1105177 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ee18e2d1c38508b93fe9ca1a03cc9bbb7c3903e0119337791e8685d31b2cede9" } } ], "extra": [ 1, 177, 237, 50, 115, 252, 162, 193, 169, 102, 150, 185, 223, 152, 212, 49, 60, 5, 162, 183, 232, 175, 244, 246, 96, 70, 18, 142, 47, 251, 206, 11, 54, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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