Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c11567b1df365cb8f40dc4b120ef665fdb11ada6f2c4829b159d83bd90f72caf

Tx prefix hash: 5fd2e676e092bd9168d692306cdf7c7ca8f816a587a155da0471debf36a97b12
Tx public key: f494049032743b9e11aa97d96914f9072cb624dc4d2ede4b93ba4a4a9750b964
Timestamp: 1758180089 Timestamp [UCT]: 2025-09-18 07:21:29 Age [y:d:h:m:s]: 00:133:07:28:30
Block: 1370983 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95265 RingCT/type: yes/0
Extra: 01f494049032743b9e11aa97d96914f9072cb624dc4d2ede4b93ba4a4a9750b964021100000007ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b3bf8ea8644e4a5315cdafc8bb9325a35b84eff9e2dd6cde58e23245ca030753 0.600000000000 1859060 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": 1370993, "vin": [ { "gen": { "height": 1370983 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b3bf8ea8644e4a5315cdafc8bb9325a35b84eff9e2dd6cde58e23245ca030753" } } ], "extra": [ 1, 244, 148, 4, 144, 50, 116, 59, 158, 17, 170, 151, 217, 105, 20, 249, 7, 44, 182, 36, 220, 77, 46, 222, 75, 147, 186, 74, 74, 151, 80, 185, 100, 2, 17, 0, 0, 0, 7, 173, 121, 72, 208, 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