Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fabeef3d55242ca74e82959711992f663e13914827863918c93cc04c14ad70a

Tx prefix hash: 2fb46e68130b7e64bed26ae945d7fa4c5d71a3990e3436f240b57504b2958a26
Tx public key: 9d34e795d8cfa51ae5b854926e28d10079b2377363a51e9a71871c16c54b8e8b
Timestamp: 1730761557 Timestamp [UCT]: 2024-11-04 23:05:57 Age [y:d:h:m:s]: 00:019:09:00:53
Block: 1146684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13872 RingCT/type: yes/0
Extra: 019d34e795d8cfa51ae5b854926e28d10079b2377363a51e9a71871c16c54b8e8b021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f32d910e19b45b559cda888f78d0bbeec8eef907b98a71fe7ea19d4095e9a1ee 0.600000000000 1631375 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": 1146694, "vin": [ { "gen": { "height": 1146684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f32d910e19b45b559cda888f78d0bbeec8eef907b98a71fe7ea19d4095e9a1ee" } } ], "extra": [ 1, 157, 52, 231, 149, 216, 207, 165, 26, 229, 184, 84, 146, 110, 40, 209, 0, 121, 178, 55, 115, 99, 165, 30, 154, 113, 135, 28, 22, 197, 75, 142, 139, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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