Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44a81524382359dfeaa11518c4730f87c2b18355a28003e4f6f84e5ba9ce85e8

Tx prefix hash: 68898e0cfe8a6adac8934150f92372fc26d963acb59be37c3212667f192351ff
Tx public key: 36c8d8789c3db571a35e10e55279722a6a078967a9d7f0c8c9b65d1af4af67c7
Timestamp: 1715156444 Timestamp [UCT]: 2024-05-08 08:20:44 Age [y:d:h:m:s]: 00:315:01:51:30
Block: 1017416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225221 RingCT/type: yes/0
Extra: 0136c8d8789c3db571a35e10e55279722a6a078967a9d7f0c8c9b65d1af4af67c702110000000b52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cbeb463cc1c462a3e969173b5b85a56b8235559fc54bc40e31dea9fc7d1ebca3 0.600000000000 1481199 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": 1017426, "vin": [ { "gen": { "height": 1017416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbeb463cc1c462a3e969173b5b85a56b8235559fc54bc40e31dea9fc7d1ebca3" } } ], "extra": [ 1, 54, 200, 216, 120, 156, 61, 181, 113, 163, 94, 16, 229, 82, 121, 114, 42, 106, 7, 137, 103, 169, 215, 240, 200, 201, 182, 93, 26, 244, 175, 103, 199, 2, 17, 0, 0, 0, 11, 82, 212, 126, 148, 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