Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d249747f5faad6525028e6430bb994ec536a654e03d0340f4019058c36941215

Tx prefix hash: afe7f52f2b9af725be44497b6d27db9b3b202c2ca23c9a06c9218f37061c27d7
Tx public key: 9bf6ffd6f09607e025be05ec0e4b2c91d5045b136dc30c27caa9d0c08bf2d409
Timestamp: 1717212873 Timestamp [UCT]: 2024-06-01 03:34:33 Age [y:d:h:m:s]: 00:288:23:21:29
Block: 1034455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206519 RingCT/type: yes/0
Extra: 019bf6ffd6f09607e025be05ec0e4b2c91d5045b136dc30c27caa9d0c08bf2d40902110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92697d3d2844ffd4301bb8f2878facaeadb01783e6b6f3d0123b0163ddc78707 0.600000000000 1502968 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": 1034465, "vin": [ { "gen": { "height": 1034455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92697d3d2844ffd4301bb8f2878facaeadb01783e6b6f3d0123b0163ddc78707" } } ], "extra": [ 1, 155, 246, 255, 214, 240, 150, 7, 224, 37, 190, 5, 236, 14, 75, 44, 145, 213, 4, 91, 19, 109, 195, 12, 39, 202, 169, 208, 192, 139, 242, 212, 9, 2, 17, 0, 0, 0, 6, 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