Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0145b0e49bbe27632762aa817f5c2ed75d123840cde827b7f3300369d43a365

Tx prefix hash: 1af95f05d252cdf98f2ab122c667a9aa4eb922f3b51f69a50f11131f7b64fa94
Tx public key: 43959db4b7fc53e7c3fc5b553e140a8c4d8bcaeacc67cd439275707cbb63725d
Timestamp: 1738182732 Timestamp [UCT]: 2025-01-29 20:32:12 Age [y:d:h:m:s]: 00:141:16:02:52
Block: 1207888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101159 RingCT/type: yes/0
Extra: 0143959db4b7fc53e7c3fc5b553e140a8c4d8bcaeacc67cd439275707cbb63725d021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 725639bf188c1eaaee3b2c2347d3435e38c376f05c07def851dcd971266f8cde 0.600000000000 1694615 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": 1207898, "vin": [ { "gen": { "height": 1207888 } } ], "vout": [ { "amount": 600000000, "target": { "key": "725639bf188c1eaaee3b2c2347d3435e38c376f05c07def851dcd971266f8cde" } } ], "extra": [ 1, 67, 149, 157, 180, 183, 252, 83, 231, 195, 252, 91, 85, 62, 20, 10, 140, 77, 139, 202, 234, 204, 103, 205, 67, 146, 117, 112, 124, 187, 99, 114, 93, 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