Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9402db66e7699f1301ea2446db3f7d847cf2ee63be1ed7d4e327eef6d9a2a8ce

Tx prefix hash: 03da210279d8a7cd37a4c79e2b628481e9bfb67d6de20e712331bd700595b632
Tx public key: 4bc1e8d36747a746952686a8872e29993d38e610b09977c9354d15f9afe6f745
Timestamp: 1709586545 Timestamp [UCT]: 2024-03-04 21:09:05 Age [y:d:h:m:s]: 01:245:06:48:16
Block: 971231 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434007 RingCT/type: yes/0
Extra: 014bc1e8d36747a746952686a8872e29993d38e610b09977c9354d15f9afe6f74502110000000249a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c2c54a8f58b06b77a42ee0b13e90212e7718b76a50eb3c04eb48078a317ce56 0.600000000000 1431118 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": 971241, "vin": [ { "gen": { "height": 971231 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c2c54a8f58b06b77a42ee0b13e90212e7718b76a50eb3c04eb48078a317ce56" } } ], "extra": [ 1, 75, 193, 232, 211, 103, 71, 167, 70, 149, 38, 134, 168, 135, 46, 41, 153, 61, 56, 230, 16, 176, 153, 119, 201, 53, 77, 21, 249, 175, 230, 247, 69, 2, 17, 0, 0, 0, 2, 73, 161, 133, 187, 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