Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9feadcfb110b3b25d4f09d48108ce3b4eb824200e1519be7c140603d06a50930

Tx prefix hash: 184e50e375e75b438c2e7cb2cd5e85f3b1772e290a3a228d3bfd09dc52c49444
Tx public key: a50385976f282a7ddc5fadd1d4dd9695d765e9b60f032d68be5a7a652346bfcf
Timestamp: 1715737483 Timestamp [UCT]: 2024-05-15 01:44:43 Age [y:d:h:m:s]: 00:336:11:39:47
Block: 1022216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240523 RingCT/type: yes/0
Extra: 01a50385976f282a7ddc5fadd1d4dd9695d765e9b60f032d68be5a7a652346bfcf021100000008c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91765f0e440f71046bcae03577bc0f8466460f7ca3284ee3c2921ef524aeee13 0.600000000000 1486753 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": 1022226, "vin": [ { "gen": { "height": 1022216 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91765f0e440f71046bcae03577bc0f8466460f7ca3284ee3c2921ef524aeee13" } } ], "extra": [ 1, 165, 3, 133, 151, 111, 40, 42, 125, 220, 95, 173, 209, 212, 221, 150, 149, 215, 101, 233, 182, 15, 3, 45, 104, 190, 90, 122, 101, 35, 70, 191, 207, 2, 17, 0, 0, 0, 8, 197, 69, 41, 96, 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