Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6e0e19437384471a386279d03a61c304a19dda73a8bd1719ebd1c82e93a584e

Tx prefix hash: e2676b84896b825ff0b6651d4c4ccf6a611526177ed7a5a5de2c99d909f03d9d
Tx public key: 6cd58fa536e78705e0234805d2e19a9d294f271a68fb1c8953537beae8141a30
Timestamp: 1732162386 Timestamp [UCT]: 2024-11-21 04:13:06 Age [y:d:h:m:s]: 00:133:19:08:59
Block: 1158286 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95443 RingCT/type: yes/0
Extra: 016cd58fa536e78705e0234805d2e19a9d294f271a68fb1c8953537beae8141a30021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: db23654fc70aa0774ce04ea6f873a408fcc2dfb1d93cda2c2307e6416f061e41 0.600000000000 1643915 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": 1158296, "vin": [ { "gen": { "height": 1158286 } } ], "vout": [ { "amount": 600000000, "target": { "key": "db23654fc70aa0774ce04ea6f873a408fcc2dfb1d93cda2c2307e6416f061e41" } } ], "extra": [ 1, 108, 213, 143, 165, 54, 231, 135, 5, 224, 35, 72, 5, 210, 225, 154, 157, 41, 79, 39, 26, 104, 251, 28, 137, 83, 83, 123, 234, 232, 20, 26, 48, 2, 17, 0, 0, 0, 3, 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