Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa1aa547fa50cb7b4f18d691fa1489779edfbf869895481c3988d13a73b63c80

Tx prefix hash: 9feaadac9b14d64ac9ff01db5ecd18c4cb8be2fd396ab45d7d63af0f3e167d7e
Tx public key: 87e46c1c9181e8c3a55ff1ffe5bebdf1421d3d2f7d7e863b6cc0483c44103098
Timestamp: 1702685836 Timestamp [UCT]: 2023-12-16 00:17:16 Age [y:d:h:m:s]: 01:035:11:26:25
Block: 914003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286681 RingCT/type: yes/0
Extra: 0187e46c1c9181e8c3a55ff1ffe5bebdf1421d3d2f7d7e863b6cc0483c44103098021100000005faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9982b99655ad6d046d56a854a347f56c464820c41dd8dcae3794e9f9da55df5e 0.600000000000 1371283 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": 914013, "vin": [ { "gen": { "height": 914003 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9982b99655ad6d046d56a854a347f56c464820c41dd8dcae3794e9f9da55df5e" } } ], "extra": [ 1, 135, 228, 108, 28, 145, 129, 232, 195, 165, 95, 241, 255, 229, 190, 189, 241, 66, 29, 61, 47, 125, 126, 134, 59, 108, 192, 72, 60, 68, 16, 48, 152, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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