Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 799e5443ae76b824a2665ee0f51e65dbba918b4a5113f75595a89e9e2e697d8b

Tx prefix hash: cfe109b160a50c122541c95bdadb356ea256ebb90afdceb42f0cec7b23cea630
Tx public key: 9c4a99141911c717e481120a9d34d58ec0c44360c8ea7bb4ab6dd7bf1ad1a15e
Timestamp: 1703890251 Timestamp [UCT]: 2023-12-29 22:50:51 Age [y:d:h:m:s]: 01:313:14:03:48
Block: 923994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 482950 RingCT/type: yes/0
Extra: 019c4a99141911c717e481120a9d34d58ec0c44360c8ea7bb4ab6dd7bf1ad1a15e02110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08573038ed792cd693a382887a8f33b70f5911eb9c869e9e103374c0c5b2b4ec 0.600000000000 1381736 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": 924004, "vin": [ { "gen": { "height": 923994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08573038ed792cd693a382887a8f33b70f5911eb9c869e9e103374c0c5b2b4ec" } } ], "extra": [ 1, 156, 74, 153, 20, 25, 17, 199, 23, 228, 129, 18, 10, 157, 52, 213, 142, 192, 196, 67, 96, 200, 234, 123, 180, 171, 109, 215, 191, 26, 209, 161, 94, 2, 17, 0, 0, 0, 6, 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