Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4db48ab1eea3bc736c6d3b72132566646e8408e06b03edee3a6924b528f0f7fa

Tx prefix hash: 78c40c2e440937e6c3e564a0bf2be85ab672a2f39efa5de1a1c08b41b22538f7
Tx public key: 656ba7534686aa22719cceb63e3e11c11cd38840e3b5f47d0b3d7009d02d9592
Timestamp: 1719832908 Timestamp [UCT]: 2024-07-01 11:21:48 Age [y:d:h:m:s]: 00:280:16:03:57
Block: 1056166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200533 RingCT/type: yes/0
Extra: 01656ba7534686aa22719cceb63e3e11c11cd38840e3b5f47d0b3d7009d02d959202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b6637d628fa9d6b745127e7c8f891377479da3a565a18de704a071f7d853914 0.600000000000 1526577 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": 1056176, "vin": [ { "gen": { "height": 1056166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b6637d628fa9d6b745127e7c8f891377479da3a565a18de704a071f7d853914" } } ], "extra": [ 1, 101, 107, 167, 83, 70, 134, 170, 34, 113, 156, 206, 182, 62, 62, 17, 193, 28, 211, 136, 64, 227, 181, 244, 125, 11, 61, 112, 9, 208, 45, 149, 146, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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