Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91051e365e1e02d239e38ce3f00bd9b1e90f12c41f021f020d566c082440b55f

Tx prefix hash: d83e824012c5b21f91a2fcc8cc7516429d6115f056455b2e0d2ad77351dcf74b
Tx public key: 8ea6f96655a93abc769fe9767b47563139edcde71794d7275db59f18221cd616
Timestamp: 1722733148 Timestamp [UCT]: 2024-08-04 00:59:08 Age [y:d:h:m:s]: 00:247:08:43:35
Block: 1080217 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176673 RingCT/type: yes/0
Extra: 018ea6f96655a93abc769fe9767b47563139edcde71794d7275db59f18221cd616021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11e23fd527f6464d545723d8fad194b8cf5fc19b6a761a8f0bf3c0a89eca7cb6 0.600000000000 1553490 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": 1080227, "vin": [ { "gen": { "height": 1080217 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11e23fd527f6464d545723d8fad194b8cf5fc19b6a761a8f0bf3c0a89eca7cb6" } } ], "extra": [ 1, 142, 166, 249, 102, 85, 169, 58, 188, 118, 159, 233, 118, 123, 71, 86, 49, 57, 237, 205, 231, 23, 148, 215, 39, 93, 181, 159, 24, 34, 28, 214, 22, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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