Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c2f5a9ab127f407f07c058888036383e37ce5773c82a31e8d8e951d00a5d9cb

Tx prefix hash: 95dc20be3352b32db722a19473a764cebe51ce750d504aa7e70c1683b6eac2eb
Tx public key: 51e38a811e259ba8c0215e950d038d5bc85f02386928ce853c961484a05dc4d8
Timestamp: 1732337266 Timestamp [UCT]: 2024-11-23 04:47:46 Age [y:d:h:m:s]: 00:001:01:22:19
Block: 1159736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 756 RingCT/type: yes/0
Extra: 0151e38a811e259ba8c0215e950d038d5bc85f02386928ce853c961484a05dc4d8021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccd9e92d68145ab2ae11a92f3417b5c5ffdda6197693400a4d1499de263adea9 0.600000000000 1645375 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": 1159746, "vin": [ { "gen": { "height": 1159736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccd9e92d68145ab2ae11a92f3417b5c5ffdda6197693400a4d1499de263adea9" } } ], "extra": [ 1, 81, 227, 138, 129, 30, 37, 155, 168, 192, 33, 94, 149, 13, 3, 141, 91, 200, 95, 2, 56, 105, 40, 206, 133, 60, 150, 20, 132, 160, 93, 196, 216, 2, 17, 0, 0, 0, 3, 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