Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fadd59ed5636e9166031a41e50e1d9a8f04957b8e074c4751f17f00f9791b2db

Tx prefix hash: 90367a66c86c2a78ba7a9d082b239e5bc5be729d65cc1e9ec12ca729445ffced
Tx public key: 8d5018fdeba7e80fe56e7f600390775a807b15d8fb3aeaec9b90ae5e03c1ff2a
Timestamp: 1733147063 Timestamp [UCT]: 2024-12-02 13:44:23 Age [y:d:h:m:s]: 00:145:21:46:11
Block: 1166447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104107 RingCT/type: yes/0
Extra: 018d5018fdeba7e80fe56e7f600390775a807b15d8fb3aeaec9b90ae5e03c1ff2a021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b3b4bab9a1c1e5cdf0191eb82867517ca4f3e5ca5b957717f60cc9738ccbc9e 0.600000000000 1652134 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": 1166457, "vin": [ { "gen": { "height": 1166447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b3b4bab9a1c1e5cdf0191eb82867517ca4f3e5ca5b957717f60cc9738ccbc9e" } } ], "extra": [ 1, 141, 80, 24, 253, 235, 167, 232, 15, 229, 110, 127, 96, 3, 144, 119, 90, 128, 123, 21, 216, 251, 58, 234, 236, 155, 144, 174, 94, 3, 193, 255, 42, 2, 17, 0, 0, 0, 4, 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