Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4dd6b9a2839fea121b11a4af7dc599523f6f4ce345349b15d78e8f060f31297

Tx prefix hash: 473dd0120f00c6a83be8809e0007a0aeef8bdfa2b2a368065d0a817f38beaa7a
Tx public key: f0ecae8f78ad2e0a679f813bad15a5a6667c143c329c38c9f735d59ef80caf04
Timestamp: 1720253272 Timestamp [UCT]: 2024-07-06 08:07:52 Age [y:d:h:m:s]: 00:189:09:42:33
Block: 1059648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135534 RingCT/type: yes/0
Extra: 01f0ecae8f78ad2e0a679f813bad15a5a6667c143c329c38c9f735d59ef80caf0402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41daf79041624d5352cae7b92939831434e1c4f71b0655e776e27e7dacdad126 0.600000000000 1530119 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": 1059658, "vin": [ { "gen": { "height": 1059648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41daf79041624d5352cae7b92939831434e1c4f71b0655e776e27e7dacdad126" } } ], "extra": [ 1, 240, 236, 174, 143, 120, 173, 46, 10, 103, 159, 129, 59, 173, 21, 165, 166, 102, 124, 20, 60, 50, 156, 56, 201, 247, 53, 213, 158, 248, 12, 175, 4, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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