Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4caef99a0c288346730719f732dca2eabd753111276c3533e443b311f6617d40

Tx prefix hash: 6d709e53689df389ce251f4585acb28d6da366d506812e12d1fea03e3df566a5
Tx public key: 7c08559ca24e9c755ee72625f24a04278f9f2219b37b056a41306f46be9f9950
Timestamp: 1720773396 Timestamp [UCT]: 2024-07-12 08:36:36 Age [y:d:h:m:s]: 01:119:11:20:19
Block: 1063977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 343889 RingCT/type: yes/0
Extra: 017c08559ca24e9c755ee72625f24a04278f9f2219b37b056a41306f46be9f9950021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa06763a99e55c5e9177dc83c63c924c306a2fd27517465cb7ff4b0b18c34c83 0.600000000000 1534498 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": 1063987, "vin": [ { "gen": { "height": 1063977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa06763a99e55c5e9177dc83c63c924c306a2fd27517465cb7ff4b0b18c34c83" } } ], "extra": [ 1, 124, 8, 85, 156, 162, 78, 156, 117, 94, 231, 38, 37, 242, 74, 4, 39, 143, 159, 34, 25, 179, 123, 5, 106, 65, 48, 111, 70, 190, 159, 153, 80, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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