Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13886998991f2952e0adb03c074e0832b2c5f4d41af55182a3df1b35d3cb6851

Tx prefix hash: 1789c4728a26aad50368f62641f8c24edb39ef0641c2e7976896c1f444c29053
Tx public key: f16ecffeb377da0c3e56a723d7fdb92eccdbd87d730fb6e17fd5a173d3b684f9
Timestamp: 1715040135 Timestamp [UCT]: 2024-05-07 00:02:15 Age [y:d:h:m:s]: 00:137:11:22:12
Block: 1016440 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98471 RingCT/type: yes/0
Extra: 01f16ecffeb377da0c3e56a723d7fdb92eccdbd87d730fb6e17fd5a173d3b684f90211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 38eda9dbcd038f86253aa056ef86ab05df29f6987668f6d1b2b9062654ae61fa 0.600000000000 1480025 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": 1016450, "vin": [ { "gen": { "height": 1016440 } } ], "vout": [ { "amount": 600000000, "target": { "key": "38eda9dbcd038f86253aa056ef86ab05df29f6987668f6d1b2b9062654ae61fa" } } ], "extra": [ 1, 241, 110, 207, 254, 179, 119, 218, 12, 62, 86, 167, 35, 215, 253, 185, 46, 204, 219, 216, 125, 115, 15, 182, 225, 127, 213, 161, 115, 211, 182, 132, 249, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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