Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 337e86f91269ba4a176047aaf53bbcb69106affadba684a60b195ee3b5b1ad09

Tx prefix hash: e6fa168dcab9dd41b8d2593251de99e8e4dbb31988f8aa4f6c7f3ff9a82654c1
Tx public key: f68e018a56767ce7dc4c7b2e7ee3894b41a2ad3fe6427b065de543a73f90acb9
Timestamp: 1651262723 Timestamp [UCT]: 2022-04-29 20:05:23 Age [y:d:h:m:s]: 03:000:18:07:53
Block: 490858 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 781216 RingCT/type: yes/0
Extra: 01f68e018a56767ce7dc4c7b2e7ee3894b41a2ad3fe6427b065de543a73f90acb902110000001ccb8520c2000000000000000000

1 output(s) for total of 14.507380077000 dcy

stealth address amount amount idx
00: b1e0f69a458bd4b05bff948e5f7b0bcb5b43496d95f22dc154243c27a1ea996b 14.507380077000 913939 of 0

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": 490868, "vin": [ { "gen": { "height": 490858 } } ], "vout": [ { "amount": 14507380077, "target": { "key": "b1e0f69a458bd4b05bff948e5f7b0bcb5b43496d95f22dc154243c27a1ea996b" } } ], "extra": [ 1, 246, 142, 1, 138, 86, 118, 124, 231, 220, 76, 123, 46, 126, 227, 137, 75, 65, 162, 173, 63, 230, 66, 123, 6, 93, 229, 67, 167, 63, 144, 172, 185, 2, 17, 0, 0, 0, 28, 203, 133, 32, 194, 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