Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a0bdffbc4e27652d88fee7effb2fe3b31cb9083369c55b9804b8100abde7e18

Tx prefix hash: 23a01dfa8550770add75aa7b6738aac8d86e934a8c24cfdd2b59dd57c1e006d3
Tx public key: 050bb2220cef0d15476ae6518064eb43b1b4ef41febb60ea066d6513b27a029c
Timestamp: 1730686805 Timestamp [UCT]: 2024-11-04 02:20:05 Age [y:d:h:m:s]: 01:006:13:07:36
Block: 1146076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263094 RingCT/type: yes/0
Extra: 01050bb2220cef0d15476ae6518064eb43b1b4ef41febb60ea066d6513b27a029c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1265000cf89a893f16e54e7fe34d0a7c2ea4022f875d76408a40d2972c7ab2b3 0.600000000000 1630637 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": 1146086, "vin": [ { "gen": { "height": 1146076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1265000cf89a893f16e54e7fe34d0a7c2ea4022f875d76408a40d2972c7ab2b3" } } ], "extra": [ 1, 5, 11, 178, 34, 12, 239, 13, 21, 71, 106, 230, 81, 128, 100, 235, 67, 177, 180, 239, 65, 254, 187, 96, 234, 6, 109, 101, 19, 178, 122, 2, 156, 2, 17, 0, 0, 0, 4, 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