Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5319c851ca6b94a9d79c234a1f43b2eb8f32ef28a435ee86991ab8d6957da974

Tx prefix hash: c1408b39185161d9af34accbe9137d05502171d8574cd24e8fd85cee52234ffe
Tx public key: 8a9cbb7a10c8ec2409e4791c48b690b2c4ef30e5d2485c8dc192bf8395831c69
Timestamp: 1694300336 Timestamp [UCT]: 2023-09-09 22:58:56 Age [y:d:h:m:s]: 01:208:00:38:00
Block: 844672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 409779 RingCT/type: yes/0
Extra: 018a9cbb7a10c8ec2409e4791c48b690b2c4ef30e5d2485c8dc192bf8395831c690211000000014b8f5122000000000000000000

1 output(s) for total of 0.975553493000 dcy

stealth address amount amount idx
00: 01e669be2a2c813d19acdd9abcac6918927e00da985c95ef448989a804314c85 0.975553493000 1297996 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": 844682, "vin": [ { "gen": { "height": 844672 } } ], "vout": [ { "amount": 975553493, "target": { "key": "01e669be2a2c813d19acdd9abcac6918927e00da985c95ef448989a804314c85" } } ], "extra": [ 1, 138, 156, 187, 122, 16, 200, 236, 36, 9, 228, 121, 28, 72, 182, 144, 178, 196, 239, 48, 229, 210, 72, 92, 141, 193, 146, 191, 131, 149, 131, 28, 105, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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