Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee474e0ab307fdbde6ad24ed98cd723a6a2bd502e83cabb6f7b1ef54be5c57ac

Tx prefix hash: af0a8c32f81ea52a0db185196cd346272cd4a1a0d9c701bc0884267a0c100338
Tx public key: f6be697f36b7434d47f2779fcb8fe5c54e65600b1c393a7944a145159a6b259a
Timestamp: 1707947896 Timestamp [UCT]: 2024-02-14 21:58:16 Age [y:d:h:m:s]: 00:318:00:24:42
Block: 957629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227675 RingCT/type: yes/0
Extra: 01f6be697f36b7434d47f2779fcb8fe5c54e65600b1c393a7944a145159a6b259a02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55cc7ef7c1f31efe700d5ca7b1fb2848a76159d46a3dda2cf3d93f5af4cd78d2 0.600000000000 1416949 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": 957639, "vin": [ { "gen": { "height": 957629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55cc7ef7c1f31efe700d5ca7b1fb2848a76159d46a3dda2cf3d93f5af4cd78d2" } } ], "extra": [ 1, 246, 190, 105, 127, 54, 183, 67, 77, 71, 242, 119, 159, 203, 143, 229, 197, 78, 101, 96, 11, 28, 57, 58, 121, 68, 161, 69, 21, 154, 107, 37, 154, 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