Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64fcf4999ddd03745d8da6db85e8f1c6fe587e6fc819c60228ba161616992284

Tx prefix hash: 368eb55272799c6c843c62d6dc7f447e0dc8626dff4cbac0bf03bbc05be50e22
Tx public key: 9bee316455b5f46e90e318d4adcccf5bace7bb5ccaba8b3521d457abdab08e65
Timestamp: 1722937030 Timestamp [UCT]: 2024-08-06 09:37:10 Age [y:d:h:m:s]: 00:269:15:12:53
Block: 1081901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192614 RingCT/type: yes/0
Extra: 019bee316455b5f46e90e318d4adcccf5bace7bb5ccaba8b3521d457abdab08e65021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37ef1e35fd2a843c9d5d2e20baa55ec1a354c6835a612fc0fa72f56521fed8fd 0.600000000000 1555724 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": 1081911, "vin": [ { "gen": { "height": 1081901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37ef1e35fd2a843c9d5d2e20baa55ec1a354c6835a612fc0fa72f56521fed8fd" } } ], "extra": [ 1, 155, 238, 49, 100, 85, 181, 244, 110, 144, 227, 24, 212, 173, 204, 207, 91, 172, 231, 187, 92, 202, 186, 139, 53, 33, 212, 87, 171, 218, 176, 142, 101, 2, 17, 0, 0, 0, 4, 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