Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b638ae1965804496fa45baa536c4d9ed311d2ce7281e26ac74f2dc4b2e7664cb

Tx prefix hash: 8f2184c1ac749409058589fa27d8711b8e3be01273ac0fa1366ac69687f1f1ae
Tx public key: 3a635ccc271ba81099a3b5b0efb598ce5e1ce3110289e56faa6594c3c3ce4810
Timestamp: 1710795817 Timestamp [UCT]: 2024-03-18 21:03:37 Age [y:d:h:m:s]: 01:020:16:59:01
Block: 981269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275758 RingCT/type: yes/0
Extra: 013a635ccc271ba81099a3b5b0efb598ce5e1ce3110289e56faa6594c3c3ce481002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47249a2b8dee754ea15c506e9a1e5dec029c0569fd32f817819b70a1e39a0b37 0.600000000000 1441364 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": 981279, "vin": [ { "gen": { "height": 981269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47249a2b8dee754ea15c506e9a1e5dec029c0569fd32f817819b70a1e39a0b37" } } ], "extra": [ 1, 58, 99, 92, 204, 39, 27, 168, 16, 153, 163, 181, 176, 239, 181, 152, 206, 94, 28, 227, 17, 2, 137, 229, 111, 170, 101, 148, 195, 195, 206, 72, 16, 2, 17, 0, 0, 0, 3, 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