Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2154f2d4da79fef66a3290bf4638086bff7855de859a283776cf7516c6232866

Tx prefix hash: fd2e27113cff45024b4548b525e2ad4ff972a5eab6efef4e0e0a1bab2d7e22f4
Tx public key: 9800b769a5d331aaf64bca61fcf99c7182ad41bd2f3606a7dd1c3b453c982d8d
Timestamp: 1714571020 Timestamp [UCT]: 2024-05-01 13:43:40 Age [y:d:h:m:s]: 00:362:06:25:17
Block: 1012549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258980 RingCT/type: yes/0
Extra: 019800b769a5d331aaf64bca61fcf99c7182ad41bd2f3606a7dd1c3b453c982d8d0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb7d1411160d6e1a341738879fc9edbbafa6d43ba57224ae46245cb713f0ca6f 0.600000000000 1475111 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": 1012559, "vin": [ { "gen": { "height": 1012549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb7d1411160d6e1a341738879fc9edbbafa6d43ba57224ae46245cb713f0ca6f" } } ], "extra": [ 1, 152, 0, 183, 105, 165, 211, 49, 170, 246, 75, 202, 97, 252, 249, 156, 113, 130, 173, 65, 189, 47, 54, 6, 167, 221, 28, 59, 69, 60, 152, 45, 141, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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