Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad7c11276408d98963044807a0ca40af98ca600dc2711cc824c2ae2a1c4d0045

Tx prefix hash: 747cec402f70b727ece2c1f6ecaf9bc9f7aa84edea3cc1c9af85ea1cf633d87b
Tx public key: 20930b6ea3c745c06c85c7d822a206813db6e60ea2971d13af413bf32abebef8
Timestamp: 1733841698 Timestamp [UCT]: 2024-12-10 14:41:38 Age [y:d:h:m:s]: 00:189:11:42:31
Block: 1172215 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135140 RingCT/type: yes/0
Extra: 0120930b6ea3c745c06c85c7d822a206813db6e60ea2971d13af413bf32abebef80211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d80ed6fc7291816502b1dfd4c33490bd40d41d84dd359b4e75d61bc366db44bc 0.600000000000 1658078 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": 1172225, "vin": [ { "gen": { "height": 1172215 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d80ed6fc7291816502b1dfd4c33490bd40d41d84dd359b4e75d61bc366db44bc" } } ], "extra": [ 1, 32, 147, 11, 110, 163, 199, 69, 192, 108, 133, 199, 216, 34, 162, 6, 129, 61, 182, 230, 14, 162, 151, 29, 19, 175, 65, 59, 243, 42, 190, 190, 248, 2, 17, 0, 0, 0, 4, 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