Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dacc37c6a48fd089c7038217d8fe40bb661fcbb28ec5515a15b793cc95883cca

Tx prefix hash: 10214a9e93824cb9ddeedd6334b7178c6d5f7f5f029756c7720963d82e59cd38
Tx public key: d512c93f03e5ce929e75d479ef35d6318cce86cfe937030f702ac0d8d265d621
Timestamp: 1696527566 Timestamp [UCT]: 2023-10-05 17:39:26 Age [y:d:h:m:s]: 01:099:01:03:03
Block: 863159 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332047 RingCT/type: yes/0
Extra: 01d512c93f03e5ce929e75d479ef35d6318cce86cfe937030f702ac0d8d265d62102110000000275e3f0e9000000000000000000

1 output(s) for total of 0.847219525000 dcy

stealth address amount amount idx
00: 0f66f9fd5d2d6d4666cae93b666e7e46e96f56235a6cf0f56a9d229059bffa04 0.847219525000 1317607 of 0

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": 863169, "vin": [ { "gen": { "height": 863159 } } ], "vout": [ { "amount": 847219525, "target": { "key": "0f66f9fd5d2d6d4666cae93b666e7e46e96f56235a6cf0f56a9d229059bffa04" } } ], "extra": [ 1, 213, 18, 201, 63, 3, 229, 206, 146, 158, 117, 212, 121, 239, 53, 214, 49, 140, 206, 134, 207, 233, 55, 3, 15, 112, 42, 192, 216, 210, 101, 214, 33, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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