Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d00d85477e1a7346cfbe2f1786dd570d202543b093e3eeb2da9710ef0e1f681

Tx prefix hash: 011e020062ab9ee9116465e72915aeb841a3712d2abdf507c09ef326dcbe9c25
Tx public key: 558edbcdf1f5e8b60815488677a514f64c1f0f7880e812845ea7b3a3252ccd02
Timestamp: 1740509010 Timestamp [UCT]: 2025-02-25 18:43:30 Age [y:d:h:m:s]: 00:268:19:59:00
Block: 1227118 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189896 RingCT/type: yes/0
Extra: 01558edbcdf1f5e8b60815488677a514f64c1f0f7880e812845ea7b3a3252ccd02021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1408a5db099f512f62756cac85a82117c320d07d28fa364c730ae8269b3dcde3 0.600000000000 1713991 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": 1227128, "vin": [ { "gen": { "height": 1227118 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1408a5db099f512f62756cac85a82117c320d07d28fa364c730ae8269b3dcde3" } } ], "extra": [ 1, 85, 142, 219, 205, 241, 245, 232, 182, 8, 21, 72, 134, 119, 165, 20, 246, 76, 31, 15, 120, 128, 232, 18, 132, 94, 167, 179, 163, 37, 44, 205, 2, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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