Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdb3a059e03662d1ed17dfd90491e943a6dfb71e2dffad1f5f8b66bf09bba9a5

Tx prefix hash: ebac2e3da5532c8e53b13007f69dff98528409eea99e3485e3215adf254d3a5d
Tx public key: f179f70d6da60b0ecd9244ef9620d86a3251ebd76d169cbfa4ed5aeecc3e56be
Timestamp: 1730389804 Timestamp [UCT]: 2024-10-31 15:50:04 Age [y:d:h:m:s]: 00:158:20:43:45
Block: 1143613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113364 RingCT/type: yes/0
Extra: 01f179f70d6da60b0ecd9244ef9620d86a3251ebd76d169cbfa4ed5aeecc3e56be021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 806b05c3c24c80e7ec1256286023e722674aae061bd5790158c79f87199ec141 0.600000000000 1627542 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": 1143623, "vin": [ { "gen": { "height": 1143613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "806b05c3c24c80e7ec1256286023e722674aae061bd5790158c79f87199ec141" } } ], "extra": [ 1, 241, 121, 247, 13, 109, 166, 11, 14, 205, 146, 68, 239, 150, 32, 216, 106, 50, 81, 235, 215, 109, 22, 156, 191, 164, 237, 90, 238, 204, 62, 86, 190, 2, 17, 0, 0, 0, 5, 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