Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e146d5d061942358402bfaa26a6ed6e554048b7ddda8410fcf8bda23fecbad0

Tx prefix hash: 58ac8c2a807d12bed8c219deddcf97bd6afd5f65b21336b3f9c055216be008e9
Tx public key: 7beb6f635bdbfb3d026c6b78e7c9d614d9daaf94029b9b68e27799ab9fb3e33a
Timestamp: 1729616599 Timestamp [UCT]: 2024-10-22 17:03:19 Age [y:d:h:m:s]: 01:020:01:27:11
Block: 1137246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272732 RingCT/type: yes/0
Extra: 017beb6f635bdbfb3d026c6b78e7c9d614d9daaf94029b9b68e27799ab9fb3e33a02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc94c262525738ebf5967fa5e1d1d4099c801c9630e79a5f68177c923cc3c1c3 0.600000000000 1620701 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": 1137256, "vin": [ { "gen": { "height": 1137246 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc94c262525738ebf5967fa5e1d1d4099c801c9630e79a5f68177c923cc3c1c3" } } ], "extra": [ 1, 123, 235, 111, 99, 91, 219, 251, 61, 2, 108, 107, 120, 231, 201, 214, 20, 217, 218, 175, 148, 2, 155, 155, 104, 226, 119, 153, 171, 159, 179, 227, 58, 2, 17, 0, 0, 0, 11, 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