Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4265040132f006d88f57a0f20956325b824184e8a2670a43bf089c25ff06e427

Tx prefix hash: 54afa73cf0b7d56310bf8ff241e17d0a3dc2b7f17c7a8880aba8662dbb0822a9
Tx public key: ace6e77abe702b0f79f6f3122e526bb3b54cb621e8ba5833869e86ac3120c261
Timestamp: 1729265994 Timestamp [UCT]: 2024-10-18 15:39:54 Age [y:d:h:m:s]: 00:222:09:45:30
Block: 1134372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158779 RingCT/type: yes/0
Extra: 01ace6e77abe702b0f79f6f3122e526bb3b54cb621e8ba5833869e86ac3120c2610211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 477ae33817fb7f98fda72412c6bdac2fd9dce47897a71e40e2944c6434c02262 0.600000000000 1617671 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": 1134382, "vin": [ { "gen": { "height": 1134372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "477ae33817fb7f98fda72412c6bdac2fd9dce47897a71e40e2944c6434c02262" } } ], "extra": [ 1, 172, 230, 231, 122, 190, 112, 43, 15, 121, 246, 243, 18, 46, 82, 107, 179, 181, 76, 182, 33, 232, 186, 88, 51, 134, 158, 134, 172, 49, 32, 194, 97, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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