Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84fcf6f434b75057f321e691613a866f5a06f85fe05a4d66d7ab85116fe70ae7

Tx prefix hash: 63cce2baaf5cc1e3f17859ee717eb74d089fcd2cd47071b90373cbdb5f2bb47d
Tx public key: 3cbae36f3d36c39010db9f27cea56c68e875ee4c9989e18c44e97d3961f45b16
Timestamp: 1721908695 Timestamp [UCT]: 2024-07-25 11:58:15 Age [y:d:h:m:s]: 00:312:12:21:19
Block: 1073373 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223312 RingCT/type: yes/0
Extra: 013cbae36f3d36c39010db9f27cea56c68e875ee4c9989e18c44e97d3961f45b1602110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e40b5dfea039e79df2259647ac86a1cfaff83c45a00686f00837fb2c0d1e56ba 0.600000000000 1545874 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": 1073383, "vin": [ { "gen": { "height": 1073373 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e40b5dfea039e79df2259647ac86a1cfaff83c45a00686f00837fb2c0d1e56ba" } } ], "extra": [ 1, 60, 186, 227, 111, 61, 54, 195, 144, 16, 219, 159, 39, 206, 165, 108, 104, 232, 117, 238, 76, 153, 137, 225, 140, 68, 233, 125, 57, 97, 244, 91, 22, 2, 17, 0, 0, 0, 1, 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