Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc1797235a396f814f86144d5b291564bcd294a435e8568041165c9cc6b58737

Tx prefix hash: d61606acb774148989b02c76c7204d4e51f967f8a009065759dcdf97f30741a3
Tx public key: ab6c2f07429b25c17b87eb573fc98955d59ccc155f8a63394a54e3dd34dc158c
Timestamp: 1696891507 Timestamp [UCT]: 2023-10-09 22:45:07 Age [y:d:h:m:s]: 01:197:22:47:02
Block: 866178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402520 RingCT/type: yes/0
Extra: 01ab6c2f07429b25c17b87eb573fc98955d59ccc155f8a63394a54e3dd34dc158c021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.827928345000 dcy

stealth address amount amount idx
00: e593f8589b82a9754faf3d0d2eb1685fb56538c1a52f960b0d5e7c980abfd561 0.827928345000 1320754 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": 866188, "vin": [ { "gen": { "height": 866178 } } ], "vout": [ { "amount": 827928345, "target": { "key": "e593f8589b82a9754faf3d0d2eb1685fb56538c1a52f960b0d5e7c980abfd561" } } ], "extra": [ 1, 171, 108, 47, 7, 66, 155, 37, 193, 123, 135, 235, 87, 63, 201, 137, 85, 213, 156, 204, 21, 95, 138, 99, 57, 74, 84, 227, 221, 52, 220, 21, 140, 2, 17, 0, 0, 0, 4, 230, 210, 127, 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