Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 73c2b4b17e72c21551a0712177838a63eef1c991a05792b3f11a0009b4d5f57a

Tx prefix hash: baa1d85ff766495fed3e8f74eaa695b06f307db5f3eb8be02617c266695aac12
Tx public key: c14e802708ed8d3c8ccc7434bacac88a379a52dc2ea437a60ded7781ca20bfdf
Timestamp: 1698300655 Timestamp [UCT]: 2023-10-26 06:10:55 Age [y:d:h:m:s]: 01:083:06:50:31
Block: 877877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320744 RingCT/type: yes/0
Extra: 01c14e802708ed8d3c8ccc7434bacac88a379a52dc2ea437a60ded7781ca20bfdf02110000000433af99f4000000000000000000

1 output(s) for total of 0.757232230000 dcy

stealth address amount amount idx
00: a3a4efbe899ac089dc4cdd5231d7d8053dc71ebdde7522470e8bda2dc7dd1d93 0.757232230000 1333271 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": 877887, "vin": [ { "gen": { "height": 877877 } } ], "vout": [ { "amount": 757232230, "target": { "key": "a3a4efbe899ac089dc4cdd5231d7d8053dc71ebdde7522470e8bda2dc7dd1d93" } } ], "extra": [ 1, 193, 78, 128, 39, 8, 237, 141, 60, 140, 204, 116, 52, 186, 202, 200, 138, 55, 154, 82, 220, 46, 164, 55, 166, 13, 237, 119, 129, 202, 32, 191, 223, 2, 17, 0, 0, 0, 4, 51, 175, 153, 244, 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