Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63036d0680b5596a1f85b2e1ab0c8af404f0cfe0e29f9e74b154280115ae93ac

Tx prefix hash: 73c9203536af695858b6566aae5e3f7859d0c1a5e95cbb104c9df6a0b44b5a9f
Tx public key: b06f6b39a7d648c264b0b7a73eae0e69d6eec48ae59bef485082942cb77ca227
Timestamp: 1734047615 Timestamp [UCT]: 2024-12-12 23:53:35 Age [y:d:h:m:s]: 00:179:21:45:33
Block: 1173926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128402 RingCT/type: yes/0
Extra: 01b06f6b39a7d648c264b0b7a73eae0e69d6eec48ae59bef485082942cb77ca227021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df283634c7e1ad21e4d91d123e73c81325dd47fe9e6bb1642c85a22fca53ac26 0.600000000000 1660015 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": 1173936, "vin": [ { "gen": { "height": 1173926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df283634c7e1ad21e4d91d123e73c81325dd47fe9e6bb1642c85a22fca53ac26" } } ], "extra": [ 1, 176, 111, 107, 57, 167, 214, 72, 194, 100, 176, 183, 167, 62, 174, 14, 105, 214, 238, 196, 138, 229, 155, 239, 72, 80, 130, 148, 44, 183, 124, 162, 39, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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