Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef0b2213df63019123b168c5e55f7d198992c39ff4f372860dfadc4d9ad84962

Tx prefix hash: 77f8e6cf45f8091f7c6d3648854b4e46254a35430a7af80dd3d5d2cc198f4607
Tx public key: 368b2befeb860b34a2fdbcc2275578c7df834c98cdf7d03f5e2cb2f63cda50f4
Timestamp: 1723950216 Timestamp [UCT]: 2024-08-18 03:03:36 Age [y:d:h:m:s]: 00:243:15:41:23
Block: 1090312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174017 RingCT/type: yes/0
Extra: 01368b2befeb860b34a2fdbcc2275578c7df834c98cdf7d03f5e2cb2f63cda50f4021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 758a8392e946637fdd5b2c93672e5785de3fc843df61c1f93b8bef9793f3b3b3 0.600000000000 1564935 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": 1090322, "vin": [ { "gen": { "height": 1090312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "758a8392e946637fdd5b2c93672e5785de3fc843df61c1f93b8bef9793f3b3b3" } } ], "extra": [ 1, 54, 139, 43, 239, 235, 134, 11, 52, 162, 253, 188, 194, 39, 85, 120, 199, 223, 131, 76, 152, 205, 247, 208, 63, 94, 44, 178, 246, 60, 218, 80, 244, 2, 17, 0, 0, 0, 5, 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