Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b22a41efeabf5538943571a96ba98800dd6d790d8e9d86663e0ccdcf06a39f4c

Tx prefix hash: 300ed9a3ac718191a515df103efbb4114f764bdcfe94fc1dc9b5b67b9fdb82fb
Tx public key: a78d72b04516a6d798bfb0f2e303826a0d3b76bf4c1be8d3e39b6f7389e2cd34
Timestamp: 1733457301 Timestamp [UCT]: 2024-12-06 03:55:01 Age [y:d:h:m:s]: 00:122:13:44:28
Block: 1169018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87393 RingCT/type: yes/0
Extra: 01a78d72b04516a6d798bfb0f2e303826a0d3b76bf4c1be8d3e39b6f7389e2cd340211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c33e912ae0d904dedd16e5b9adb73c4e6746c4dfeea1290179eee9c0ef07da2c 0.600000000000 1654731 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": 1169028, "vin": [ { "gen": { "height": 1169018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c33e912ae0d904dedd16e5b9adb73c4e6746c4dfeea1290179eee9c0ef07da2c" } } ], "extra": [ 1, 167, 141, 114, 176, 69, 22, 166, 215, 152, 191, 176, 242, 227, 3, 130, 106, 13, 59, 118, 191, 76, 27, 232, 211, 227, 155, 111, 115, 137, 226, 205, 52, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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