Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1a156c9241ff30409ea23257956b7a131542b9d1fe0f7a825e1051fd72c894d

Tx prefix hash: b0e227f8cb4fd86c4bf0c33be24c46ee8348e58280c9d5f223cda1b84de8a1a1
Tx public key: adae7b81b54f100abf6423adf93fb253d2d70b59a32fcc3151a9e3d664b201db
Timestamp: 1670665175 Timestamp [UCT]: 2022-12-10 09:39:35 Age [y:d:h:m:s]: 02:129:20:08:51
Block: 649431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 614508 RingCT/type: yes/0
Extra: 01adae7b81b54f100abf6423adf93fb253d2d70b59a32fcc3151a9e3d664b201db02110000000575e3f0e9000000000000000000

1 output(s) for total of 4.326786766000 dcy

stealth address amount amount idx
00: 1caac42c09a98706a31fd68a7d1608925948b422c9cb1c5d2a5f04653692cc8f 4.326786766000 1089796 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": 649441, "vin": [ { "gen": { "height": 649431 } } ], "vout": [ { "amount": 4326786766, "target": { "key": "1caac42c09a98706a31fd68a7d1608925948b422c9cb1c5d2a5f04653692cc8f" } } ], "extra": [ 1, 173, 174, 123, 129, 181, 79, 16, 10, 191, 100, 35, 173, 249, 63, 178, 83, 210, 215, 11, 89, 163, 47, 204, 49, 81, 169, 227, 214, 100, 178, 1, 219, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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