Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 279c4b9d53f67ea30611f0a7ed6f907a9b98bb521bad6b3f71c54051265aef05

Tx prefix hash: 34405b5ec4334312a53d63631275244fc44d5b5b1158434bf189c6d5b6c2d523
Tx public key: 952f76848e324ae8a43e7256f37962f3c0976d5d739dfd934ae31e483f47f1ea
Timestamp: 1700522823 Timestamp [UCT]: 2023-11-20 23:27:03 Age [y:d:h:m:s]: 01:060:12:02:13
Block: 896074 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304606 RingCT/type: yes/0
Extra: 01952f76848e324ae8a43e7256f37962f3c0976d5d739dfd934ae31e483f47f1ea021100000005faf35c9c000000000000000000

1 output(s) for total of 0.659075016000 dcy

stealth address amount amount idx
00: b5603860ec50a6cad5cb466c5db4a281a9eab994bdad34bbf51c28b866bbb6fa 0.659075016000 1352325 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": 896084, "vin": [ { "gen": { "height": 896074 } } ], "vout": [ { "amount": 659075016, "target": { "key": "b5603860ec50a6cad5cb466c5db4a281a9eab994bdad34bbf51c28b866bbb6fa" } } ], "extra": [ 1, 149, 47, 118, 132, 142, 50, 74, 232, 164, 62, 114, 86, 243, 121, 98, 243, 192, 151, 109, 93, 115, 157, 253, 147, 74, 227, 30, 72, 63, 71, 241, 234, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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