Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ea4db90c01057966743865ba08f7b22941abdcd3579fae9f2d5df18aaf8fdc8

Tx prefix hash: 064ab3799fa79f8f10fd5b6540d3a035a66e051f5694510e7f60ceb01e66938d
Tx public key: 8ba174dc24952fbc2f98f0a669bd81ad4742baf7d74f5bdcb376aba90b2f363c
Timestamp: 1715954542 Timestamp [UCT]: 2024-05-17 14:02:22 Age [y:d:h:m:s]: 00:233:18:42:25
Block: 1024026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167320 RingCT/type: yes/0
Extra: 018ba174dc24952fbc2f98f0a669bd81ad4742baf7d74f5bdcb376aba90b2f363c02110000000279bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5aec4facdd64a618bdd989272d08103ec0f512d52d701c3546307b704f01ccf9 0.600000000000 1489443 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": 1024036, "vin": [ { "gen": { "height": 1024026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5aec4facdd64a618bdd989272d08103ec0f512d52d701c3546307b704f01ccf9" } } ], "extra": [ 1, 139, 161, 116, 220, 36, 149, 47, 188, 47, 152, 240, 166, 105, 189, 129, 173, 71, 66, 186, 247, 215, 79, 91, 220, 179, 118, 171, 169, 11, 47, 54, 60, 2, 17, 0, 0, 0, 2, 121, 189, 163, 190, 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