Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 449b35f1cdbd3b9ec61523873bdd9551af3dc01dc950da56165c425d094f1933

Tx prefix hash: f8c7af71693a01dcfa551c6ae1dc778cbb91399c188dcb5bf54b7584660c1191
Tx public key: a2d6a40ca8c68ac7c66564721c1f3471c7e734897a6bbf7f630df635e7b271a3
Timestamp: 1712084357 Timestamp [UCT]: 2024-04-02 18:59:17 Age [y:d:h:m:s]: 00:270:16:01:30
Block: 991898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193780 RingCT/type: yes/0
Extra: 01a2d6a40ca8c68ac7c66564721c1f3471c7e734897a6bbf7f630df635e7b271a302110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 862ea7369f27632a6a7b38faf824afb01d4e8a7426578513e0cb9c673ffd3aaf 0.600000000000 1452234 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": 991908, "vin": [ { "gen": { "height": 991898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "862ea7369f27632a6a7b38faf824afb01d4e8a7426578513e0cb9c673ffd3aaf" } } ], "extra": [ 1, 162, 214, 164, 12, 168, 198, 138, 199, 198, 101, 100, 114, 28, 31, 52, 113, 199, 231, 52, 137, 122, 107, 191, 127, 99, 13, 246, 53, 231, 178, 113, 163, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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