Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a3e7d64bff4fe4d249a1691de8158c4f2ec61f9c8180d8781bb153e5f333f84

Tx prefix hash: 523da0f94f884c7e75739e2c79b693f5083fbc96020ef5c6253f73157d778d69
Tx public key: 5436f6137cbf7a533269dd11f819ad24935a4a89e915d9644972f6e486a17be4
Timestamp: 1723119937 Timestamp [UCT]: 2024-08-08 12:25:37 Age [y:d:h:m:s]: 00:141:23:08:47
Block: 1083420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101565 RingCT/type: yes/0
Extra: 015436f6137cbf7a533269dd11f819ad24935a4a89e915d9644972f6e486a17be402110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a29487954a37f7d3cf343bbe4270e499d7b23f2e111a9489cd57bce531b47936 0.600000000000 1557331 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": 1083430, "vin": [ { "gen": { "height": 1083420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a29487954a37f7d3cf343bbe4270e499d7b23f2e111a9489cd57bce531b47936" } } ], "extra": [ 1, 84, 54, 246, 19, 124, 191, 122, 83, 50, 105, 221, 17, 248, 25, 173, 36, 147, 90, 74, 137, 233, 21, 217, 100, 73, 114, 246, 228, 134, 161, 123, 228, 2, 17, 0, 0, 0, 10, 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