Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 96846ac49e80fd3e994ed5da9bb206891c5dcfff549a0d9c7ce378e21d915e4a

Tx prefix hash: b22bdc79dd1daed45c391a9adf85439b1fd3909fedd82c1ae2f3135f29f02484
Tx public key: 1a26f765a863050c1f94cae6f128185fd6458bb7cef847f68df579e2a4774bf1
Timestamp: 1713122717 Timestamp [UCT]: 2024-04-14 19:25:17 Age [y:d:h:m:s]: 01:037:17:56:15
Block: 1000517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287975 RingCT/type: yes/0
Extra: 011a26f765a863050c1f94cae6f128185fd6458bb7cef847f68df579e2a4774bf102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6d5c77f467fa955860f0a6ad14b13d269b2262ab4fb1dceaa7ceda4a983146f 0.600000000000 1461015 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": 1000527, "vin": [ { "gen": { "height": 1000517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6d5c77f467fa955860f0a6ad14b13d269b2262ab4fb1dceaa7ceda4a983146f" } } ], "extra": [ 1, 26, 38, 247, 101, 168, 99, 5, 12, 31, 148, 202, 230, 241, 40, 24, 95, 214, 69, 139, 183, 206, 248, 71, 246, 141, 245, 121, 226, 164, 119, 75, 241, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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