Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2731723c68bedc0effa21ac99b38fade4b8eae313bf5b395c15d8049f44da9d4

Tx prefix hash: 455a2a1fd77ee49b13c26b21cf90a04abf839a22903d14eff48da82ba9b10155
Tx public key: 016e7123d050243ad8d52f7551ccdef6a2a5331f1c44ee64d2b7d62865d36d5c
Timestamp: 1742821546 Timestamp [UCT]: 2025-03-24 13:05:46 Age [y:d:h:m:s]: 00:238:14:01:35
Block: 1246273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168259 RingCT/type: yes/0
Extra: 01016e7123d050243ad8d52f7551ccdef6a2a5331f1c44ee64d2b7d62865d36d5c021100000017c6740958000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3708f03174b242089a449c8f9078a00aad1b0fe5167c9cfd7bad37304706c9d8 0.600000000000 1733274 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": 1246283, "vin": [ { "gen": { "height": 1246273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3708f03174b242089a449c8f9078a00aad1b0fe5167c9cfd7bad37304706c9d8" } } ], "extra": [ 1, 1, 110, 113, 35, 208, 80, 36, 58, 216, 213, 47, 117, 81, 204, 222, 246, 162, 165, 51, 31, 28, 68, 238, 100, 210, 183, 214, 40, 101, 211, 109, 92, 2, 17, 0, 0, 0, 23, 198, 116, 9, 88, 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