Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c01f1a02fb0146d76ae3a2d046e8ba40d76344a1833fbcbd9856893425860ac1

Tx prefix hash: 036821f7134a4749535911bfa2fa1d0a98599f85b2e77bf7e937756ec607b101
Tx public key: e39ad5b21fb718f9993fd105fdf9871237e13e9165e2198cac84f8c2d62bdfb4
Timestamp: 1726576109 Timestamp [UCT]: 2024-09-17 12:28:29 Age [y:d:h:m:s]: 00:224:03:53:19
Block: 1112076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160053 RingCT/type: yes/0
Extra: 01e39ad5b21fb718f9993fd105fdf9871237e13e9165e2198cac84f8c2d62bdfb402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea3c69366c41636f71928c35d78a22e26746e85bae7a44b57d50df76d769045f 0.600000000000 1591269 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": 1112086, "vin": [ { "gen": { "height": 1112076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea3c69366c41636f71928c35d78a22e26746e85bae7a44b57d50df76d769045f" } } ], "extra": [ 1, 227, 154, 213, 178, 31, 183, 24, 249, 153, 63, 209, 5, 253, 249, 135, 18, 55, 225, 62, 145, 101, 226, 25, 140, 172, 132, 248, 194, 214, 43, 223, 180, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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