Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b8dd603bacdb9209b1a03b1f20102e935c09323cb6b01775636786e5de597bc

Tx prefix hash: cfde0e6d612c9fc071f9231c6cb63e942887930db893fb34653d7c3b1114db67
Tx public key: 2a2d2dd9d52dcf05d3f3d2a4841f015984d449f0f2f33906c2d95cf84bcc2823
Timestamp: 1722540567 Timestamp [UCT]: 2024-08-01 19:29:27 Age [y:d:h:m:s]: 01:094:08:25:36
Block: 1078608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325922 RingCT/type: yes/0
Extra: 012a2d2dd9d52dcf05d3f3d2a4841f015984d449f0f2f33906c2d95cf84bcc2823021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e79e414ce4dc458b3df86aa13aca709faa5178f5cd57e7d41e55f5bdd276f3f 0.600000000000 1551213 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": 1078618, "vin": [ { "gen": { "height": 1078608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e79e414ce4dc458b3df86aa13aca709faa5178f5cd57e7d41e55f5bdd276f3f" } } ], "extra": [ 1, 42, 45, 45, 217, 213, 45, 207, 5, 211, 243, 210, 164, 132, 31, 1, 89, 132, 212, 73, 240, 242, 243, 57, 6, 194, 217, 92, 248, 75, 204, 40, 35, 2, 17, 0, 0, 0, 2, 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